-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Golang to 1.12.1 #11330
Update Golang to 1.12.1 #11330
Conversation
Went through the changelog and also stumbled over TLS changes: https://golang.org/doc/go1.12 @ph I don't think it will have an affect but you should double check. Overall +1 on going to 1.12. |
@ruflin I would like to add support for TLS 1.3 |
ce055eb
to
069b5f3
Compare
@@ -1,4 +1,4 @@ | |||
FROM golang:1.10.3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ruflin Do you know why the version of Golang differed from other Beats versions? Is it ok to update it?
I haven't seen any related failures yet.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is odd, all Beats should be in sync :-( I assume this had only an affect on testing and not packaging, meaning in 7.0 all Beats are packaged with the same Golang version.
Please update, I assume we missed it in the last Golang update.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was downgraded here: https://github.com/elastic/beats/pull/9242/files#diff-69f23758930df5eda4eeb23437b8a2ccR1
It seems like an accidental change. Or at least I haven't seen any reasoning why it was done.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It probably was a merge gone bad.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sayden Can you please open a PR with reverting to the old Dockerfile?
We might want to look at using this:
|
Something to keep in mind on SDH |
Looking at the TLSv1.3, from my understanding you need to opt-in via an environment variables, not sure if can force it via a TLSConfig. |
While it hasn't been kept up so far, should the various golang.org/x packages be kept in sync with this update too? These are currently vendored:
|
@graphaelli correct, I think we were just updating them as needed or when a bug was detected (mostly following what ain't broke don't fix it..). I think we should clarify that strategy and I would be +1 to keep them in sync. Wdyt @ruflin? |
@ph We could document that adding the environment variable lets you use TLSv3. But it's not so user friendly. Or we could add the feature regardless and release it officially when we update Go to 1.13. :D @graphaelli @ph 👍 for keeping these packages in sync |
1c6f729
to
8c451b8
Compare
+1 to keep the libs in sync. |
@@ -170,7 +170,7 @@ type InterfaceAddress struct { | |||
// BPF is a compiled filter program, useful for offline packet matching. | |||
type BPF struct { | |||
orig string | |||
bpf _Ctype_struct_bpf_program // takes a finalizer, not overriden by outsiders | |||
bpf C.struct_bpf_program // takes a finalizer, not overriden by outsiders |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not really familiar with this change. @tsg could you have a look?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
He merged the PR in his own repo. So he already accepted it. :)
|
||
// This binary tests that PCAP packet capture is working correctly by issuing | ||
// HTTP requests, then making sure we actually capture data off the wire. | ||
package main |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the removal of this file related to 1.12.1?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was removed by govendor when I ran fetch
. I thought it was removed from the original repo... But now I see that it's still there. Let me look into why the tool got rid of this file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The reason could be that its package main
. My first gest was that it's a test file, but it's a script.
CI Failure looks related. |
232543b
to
7c28ffb
Compare
e9e2008
to
89d0de2
Compare
9ddca5e
to
adddf0c
Compare
Can this be backported into backport into 7.0/7.x? I only see it in master. (Context: I ran into this tonight) |
Changes in 1.12: https://golang.org/doc/go1.12 Changes in minor release: https://github.com/golang/go/issues?q=milestone%3AGo1.12.1 Updated vendored packages: - `github.com/tsg/gopacket/pcap` - `github.com/docker/docker/pkg/*` - `github.com/docker/go-connections` New vendored packages (as required by dependencies): - `github.com/konsorten/go-windows-terminal-sequences` Removed vendored package: - `github.com/Sirupsen/logrus`: `github.com/sirupsen/logrus` is used and it leads to a case insensitive collision, required by docker dependencies
Changes in 1.12: https://golang.org/doc/go1.12
Changes in minor release: https://github.com/golang/go/issues?q=milestone%3AGo1.12.1
Updated vendored packages:
github.com/tsg/gopacket/pcap
github.com/docker/docker/pkg/*
github.com/docker/go-connections
New vendored packages (as required by dependencies):
github.com/konsorten/go-windows-terminal-sequences
Removed vendored package:
github.com/Sirupsen/logrus
:github.com/sirupsen/logrus
is used and it leads to a case insensitive collision, required by docker dependenciesTODO
github.com/tsg/gopacket/pcap
Cgo changeslogp
Possibly interesting PR to devs @elastic/apm-server